Apparatus, Methods and Systems for Testing Connected Services in a Vehicle

ABSTRACT

Various embodiments include tools and methods for diagnosing connected services in a vehicle. Communication with a vehicle computing system in a vehicle may be established. A diagnostic connection to a diagnostics server may also be established. Vehicle information and diagnostic data from one or more connected services may be received from the vehicle computing system and transmitted via a diagnostic connection to the diagnostics server. A connected services diagnostic status for the vehicle may be determined based on the vehicle information and the diagnostic data. The connected services diagnostic status may be received from the server and output to a user.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.12/844,409 filed Jul. 27, 2010, the disclosure of which is herebyincorporated in its entirety by reference herein.

TECHNICAL FIELD

Various embodiments relate to testing connected service in a vehicle.

BACKGROUND

Various tools exist in the art for diagnostic vehicle services. Forexample, U.S. Pat. No. 7,590,476 to Shumate discloses a vehiclediagnosis system and method. Vehicle faults are diagnosed by receivinginformation on a vehicle from a customer regarding an actual vehiclefault and accessing data regarding the actual vehicle fault from thevehicle. A diagnostic program is initiated based on identifying vehicleinformation, the information received from the customer, and the dataaccessed from the vehicle. A specific vehicle system is selected fordiagnosis and includes a particular vehicle component that may beassociated with the actual vehicle fault. A list of diagnostic programresults is received that defines multiple probable vehicle componentfaults for the specific vehicle system that may be associated with theactual vehicle fault. A determination on how to proceed with correctingthe actual vehicle fault is made based on the list of diagnostic programresults that define multiple probable vehicle component faults. Aprobable vehicle component fault is selected to evaluate whether it isthe source of the actual vehicle fault.

SUMMARY

One aspect includes a diagnostic system for diagnosing one or moreconnected services in a vehicle. The system may include at least oneconnected services diagnostic computer (e.g., and without limitation, ahandheld computer) which may include diagnostic software for diagnosingone or more connected services of a vehicle. The connected services mayinclude, but is not limited to, at least one of a WiFi service, aBLUETOOTH service, a storage media service, an in-vehicle memory cardreader service, and an audio service.

The diagnostic computer may be configured to establish wired and/orwireless communication with a vehicle computing system in the vehicle.The computer may be further configured to establish a diagnosticconnection (which may be a wireless connection) to a diagnostics server.Vehicle information and diagnostic data from the one or more connectedservices may be received from the vehicle computing system. The vehicleinformation and the diagnostic data may be transmitted via thediagnostic connection to the diagnostics server. A connected servicesdiagnostic status may be determined for the vehicle based on the vehicleinformation and the diagnostic data. The connected services diagnosticstatus may be received from the server via the diagnostic connection andoutput to a user.

In one embodiment, the connected services diagnostic status may be basedon diagnostic information stored in a diagnostics database.

Another aspect includes a computer program product for diagnosing one ormore connected services in a vehicle. The computer program product maybe embodied in a computer readable medium and have computer readableinstructions for establishing communication with a vehicle computingsystem in the vehicle. Additional instructions may be for establishing adiagnostic connection to a diagnostics server. Vehicle information anddiagnostic data from the one or more connected services may be receivedfrom the vehicle computing system and transmitted via the diagnosticconnection to the diagnostics server. A connected services diagnosticstatus may be determined for the vehicle based on the vehicleinformation and the diagnostic data. The connected services diagnosticstatus may be received from the server via the diagnostic connection andoutput to a user.

In one embodiment, the connected services diagnostic status may be apass/fail status. The output may further include a cause and location ofa connected services failure if the diagnostic status is a fail status.

Another aspect includes a method for diagnosing one or more connectedservices in a vehicle. Vehicle and diagnostic communication may beestablished via a vehicle connection and a diagnostic connection,respectively. Vehicle information and connected services diagnostic datafor a vehicle may be received via the vehicle connection and transmittedvia the diagnostic connection to a server. A connected servicesdiagnostic status may be determined using the vehicle information andthe diagnostic data. A diagnostic status may be received and output to auser.

In one embodiment, the vehicle information may be used to identify avehicle and the diagnostic data may be used to determine the diagnosticstatus from a diagnostic database. The vehicle information may be avehicle identification number (VIN).

In additional embodiments, the output may be received on a handheldcomputer on which one or more LED lights are illuminated to signify thediagnostic status.

These and other aspects of the present invention will be betterunderstood in view of the attached drawings and following detaileddescription of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The figures identified below are illustrative of some embodiments of thepresent invention. The figures are not intended to be limiting of theinvention recited in the appended claims. Embodiments of the presentinvention, both as to their organization and manner of operation,together with further object and advantages thereof, may best beunderstood with reference to the following description, taken inconnection with the accompanying drawings, in which:

FIG. 1 is an illustration of the system architecture of a vehiclecomputing system according to one of the various embodiments;

FIG. 2A illustrates one embodiment of a connected service test tool fortesting wireless functions in a vehicle;

FIG. 2B is a dissected view of the connected services test tool shown inFIG. 2A according to one of the various embodiments;

FIG. 3 illustrates a system architecture for obtaining diagnosticinformation for one or more in-vehicle connected services according toone of the various embodiments; and

FIG. 4 illustrates one process for testing and diagnosing one or morewireless, connected services in a vehicle according to one of thevarious embodiments.

DETAILED DESCRIPTION

As required, detailed embodiments of the present invention are disclosedherein; however, it is to be understood that the disclosed embodimentsare merely exemplary of the invention that may be embodied in variousand alternative forms. The figures are not necessarily to scale; somefeatures may be exaggerated or minimized to show details of particularcomponents. Therefore, specific structural and functional detailsdisclosed herein are not to be interpreted as limiting, but merely as arepresentative basis for teaching one skilled in the art to variouslyemploy the present invention.

Detailed embodiments of the present invention are disclosed herein.However, it is to be understood that the disclosed embodiments aremerely exemplary of an invention that may be embodied in various andalternative forms. Therefore, specific functional details disclosedherein are not to be interpreted as limiting, but merely as arepresentative basis for the claims and/or as a representative basis forteaching one skilled in the art to variously employ the presentinvention.

FIG. 1 illustrates an example block topology for a vehicle basedcomputing system 1 for a vehicle 31. A vehicle enabled with avehicle-based computing system may contain a visual front end interface4 located in the vehicle. The user may also be able to interact with theinterface if it is provided, for example, with a touch sensitive screen.In another illustrative embodiment, the interaction occurs through,button presses, audible speech and speech synthesis.

In the illustrative embodiment 1 shown in FIG. 1, a processor 3 controlsat least some portion of the operation of the vehicle-based computingsystem. Provided within the vehicle, the processor allows onboardprocessing of commands and routines. Further, the processor is connectedto both non-persistent 5 and persistent storage 7. In this illustrativeembodiment, the non-persistent storage is random access memory (RAM) andthe persistent storage is a hard disk drive (HDD) or flash memory.

The processor is also provided with a number of different inputsallowing the user to interface with the processor. In this illustrativeembodiment, a microphone 29, an auxiliary input 25 (for input 33), a USBinput 23, a GPS input 24 and a BLUETOOTH input 15 are all provided. Aninput selector 51 is also provided, to allow a user to swap betweenvarious inputs. Input to both the microphone 29 and the auxiliaryconnector 25 may be converted from analog to digital by a converter 27before being passed to the processor.

Outputs to the system can include, but are not limited to, a visualdisplay 4 and a speaker 13 or stereo system output. The speaker isconnected to an amplifier 11 and receives its signal from the processor3 through a digital-to-analog converter 9. Output can also be made to aremote BLUETOOTH device such as PND 54 or a USB device such as vehiclenavigation device 60 along the bi-directional data streams shown at 19and 21 respectively.

In one illustrative embodiment, the system 1 uses the BLUETOOTHtransceiver 15 to communicate 17 with a user's nomadic device 53 (e.g.,cell phone, smart phone, PDA, etc.). The nomadic device (ND) can then beused to communicate 59 with a network 61 outside the vehicle 31 through,for example, communication 55 with a cellular tower 57.

Exemplary communication between the nomadic device and the BLUETOOTHTransceiver is represented by signal 14.

Pairing a nomadic device 53 and the BLUETOOTH transceiver 15 can beinstructed through a button 52 or similar input. Accordingly, the CPU isinstructed that the onboard BLUETOOTH transceiver will be paired with aBLUETOOTH transceiver in a nomadic device.

Data may be communicated between CPU 3 and network 61 utilizing, forexample, a data-plan, data over voice, or DTMF tones associated withnomadic device 53. Alternatively, it may be desirable to include anonboard modem 63 having antenna 18 in order to communicate 16 databetween CPU 3 and network 61 over the voice band. The nomadic device 53can then be used to communicate 59 with a network 61 outside the vehicle31 through, for example, communication 55 with a cellular tower 57. Insome embodiments, the modem 63 may establish communication 20 with thetower 57 for communicating with network 61. As a non-limiting example,modem 63 may be a USB cellular modem and communication 20 may becellular communication.

In one illustrative embodiment, the processor is provided with anoperating system including an API to communicate with modem applicationsoftware. The modem application software may access an embedded moduleor firmware on the BLUETOOTH transceiver to complete wirelesscommunication with a remote BLUETOOTH transceiver (such as that found ina nomadic device).

In another embodiment, nomadic device 53 includes a modem for voice bandor broadband data communication. In the data-over-voice embodiment, atechnique known as frequency division multiplexing may be implementedwhen the owner of the nomadic device can talk over the device while datais being transferred. At other times, when the owner is not using thedevice, the data transfer can use the whole bandwidth (300 Hz to 3.4 kHzin one example).

If the user has a data-plan associated with the nomadic device, it ispossible that the data-plan allows for broad-band transmission and thesystem could use a much wider bandwidth (speeding up data transfer). Instill another embodiment, nomadic device 53 is replaced with a cellularcommunication device (e.g., and without limitation, modem 63) that isinstalled to vehicle 31. In yet another embodiment, the ND 53 may be awireless local area network (LAN) device capable of communication over,for example (and without limitation), an 802.11g network (i.e., WiFi) ora WiMax network.

In one embodiment, incoming data can be passed through the nomadicdevice via a data-over-voice or data-plan, through the onboard BLUETOOTHtransceiver and into the vehicle's internal processor 3. In the case ofcertain temporary data, for example, the data can be stored on the HDDor other storage media 7 until such time as the data is no longerneeded.

Additional sources that may interface with the vehicle include apersonal navigation device 54, having, for example, a USB connection 56and/or an antenna 58, a vehicle navigation device 60 having a USB 62 orother connection, an onboard GPS device 24, or remote navigation system(not shown) having connectivity to network 61.

Further, the CPU could be in communication with a variety of otherauxiliary devices 65. These devices can be connected through a wireless67 or wired 69 connection. Also, or alternatively, the CPU could beconnected to a vehicle based wireless router 73, using for example aWiFi 71 transceiver. This could allow the CPU to connect to remotenetworks in range of the local router 73.

FIGS. 2A and 2B show a tool for testing and diagnosing one or moreconnected services in a vehicle. FIG. 2B is a dissected view of the toolshown in FIG. 2A. It will be appreciated that the architecture andarrangement of the components in FIGS. 2A and 2B are non-limiting. Thearrangement of parts may be modified without departing from the one ormore embodiments of the invention. Furthermore, those of skill in theart will appreciate that the external configuration of tool 100 is notlimited to the particular configuration illustrated in FIGS. 2A and 2Bas described above. A multitude of different shapes and configurationsmay be implemented. For example, the test tool 100 may be implemented insoftware running on a portable computing device, such as a laptopcomputer, handheld computer or other mobile computing device.Alternatively or additionally, the tool may be a web-based tool. Theshape and physical configuration of the tool illustrated in FIGS. 2A and2B should not be construed as a limitation of the present invention.

The features of tool 100, as described below, may or may not beintegrated as part of a tool for testing one or more communicationchannel inputs to a vehicle computing system. One such tool is describedin application Ser. No. 12/126,624 entitled, “Apparatus and Method forRemotely Testing Multiple Communication Channel Inputs to a VehicleComputer,” the contents of which are incorporated herein by reference.

Referring to FIG. 2A, tool 100 may be a handheld or other electronicdevice having a display 102 for displaying status messages (graphicaland/or tactile) to a user. Alternatively, tool 100 may not be a handhelddevice and may include, for example (and without limitation) a desktopcomputer or laptop computer. The status messages may pertain to thestatus of the connected services being tested in the vehicle. It shouldbe understood that “connected services” refers to connections to one ormore in-vehicle services (e.g., and without limitation, BLUETOOTH, WiFi,memory card reader, GPS, etc).

In some embodiments, the display 102 may also be used to display videoimages during video testing. In this non-limiting embodiment, theauxiliary input may be a video input 25 (e.g., and without limitation,an RCA jack) for receiving a video testing cable on tool 100 (notshown).

Connected services that may be tested may include wireless and wiredservices including, but not limited to, WiFi, WiMax, LAN, WAN,BLUETOOTH, audio sounds, video signals, and memory card and memory cardslot functionality. Additional, non-limiting connected services that maybe tested include in-vehicle software. As a non-limiting example,in-vehicle software may be tested for connection status, presence oflicense keys, and software level status (i.e., the amount of downloadedsoftware). A user may seek to diagnose one or more of these connectedservices in a vehicle using tool 100.

Tool 100 may include a speaker 104 for diagnosing audio sound qualityand vehicle speaker complaints. In diagnosing the audio sound, one ormore audible sounds may be output from speaker 104 signifying the audiosound's operability or inoperability. The audible diagnostic sounds mayinclude, but are not limited to, one or more tones, beeps, or otheralerts. In one non-limiting embodiment, speaker 104 may output anoperability result in a spoken language. For example, and withoutlimitation, one or more spoken messages such as “audio is working” maybe output.

One or more connectors may be connected to one or more inputs of thevehicle for use in diagnosing one or more connected services. Tool 100may include both wired and wireless inputs/connections. A wireless inputmay include input 106. Tool input 106 may wirelessly connect (e.g., andwithout limitation, via WiFi, WiMax, cellular and/or BLUETOOTH) tovehicle computing system 1 as part of the connected services testing ofthe wireless components. Based on the connectivity status, theconnectivity of the wireless module in the vehicle can be diagnosed.Further details of the wireless input will be described with respect toFIG. 2B.

A wired vehicle input/connection may include input 108. Tool input 108may be used to diagnose memory card slots in vehicles equipped with amemory card reader. Input 108 may be inserted into a memory card slot inthe vehicle and the connectivity status of the memory card readerdisplayed on display 102 and/or output from speaker 104.

A wired tool input may also include a video diagnostic input (not shown)as described above).

In one embodiment, tool 100 may also include an adapter slot 110 (FIG.2B) for diagnosing storage media such as (and without limitation) amemory card (e.g., secure digital (SD), compact flash (CF), etc.), aPCMCIA card, or other like media. The adapter slot 110 may be anysuitable port for connecting a storage media diagnostic deviceincluding, but not limited to, a USB port, a firewire port, serial port,and/or parallel port. In some embodiments, the adapter port 110 maypermit the storage media diagnostic devices to be interchanged fordiagnosing multiple media. In some further embodiments, adapter slot 110may receive the storage media directly. As a non-limiting example, amemory card may be inserted into the adapter slot 110 for obtaining adiagnosis of the memory card. In any embodiment, the diagnosis may beoutput on display 102 and/or audibly from speaker 104.

As will be further described below, a diagnosis of the one or morevehicle modules may be accomplished over a communication network (e.g.,and without limitation, the Internet). FIG. 3 illustrates a systemarchitecture for obtaining diagnostic information at tool 100 for one ormore connected services in a vehicle. FIG. 3 will be described withrespect to FIGS. 2A and 2B.

FIG. 2A illustrates connection 112 of tool 100 which may be a wiredconnection to the vehicle. Vehicle connector 112 may be, but is notlimited to, a USB, serial, or parallel connection. By insertingconnection 112 to a vehicle port (e.g., and without limitation, a USB,serial or parallel port), vehicle identification information (such as avehicle identification number or VIN) may be obtained by tool 100. TheVIN may be obtained through a vehicle network, through a lookup processon a vehicle module, through an OBD module, and/or via softwareinstalled to the VCS 1. It will be appreciated that vehicle informationmay be obtained through other tools and those provided are provided asnon-limiting examples. The vehicle identification information obtainedby the tool 100 may be transmitted to a vehicle information database 206over a communication network 202.

In one non-limiting embodiment, the communication network may be theInternet. The communication standard(s) for transmitting the vehicleinformation may include, but are not limited to, cellular, WiFi, andWiMax. Communication network 202 may serve as a diagnostic connectionover which information may be transmitted to the server 204 andinformation from the vehicle information database 206 may be receivedfor determining a diagnostic status of the one or more connected servicein the vehicle.

As illustrated in FIG. 3, in one embodiment, the vehicle informationdatabase 206 may be hosted or controlled by an OEM or other entity andaccessed through server 204. Information obtained from the vehicle (suchas, without limitation, VINs) may be transmitted to the OEM backendsystem 204 via the diagnostic connection (network 202). The vehicleinformation database 206 may include diagnostic information records onone or more vehicles. Non-limiting examples of vehicle diagnosticinformation may include information on software/hardware located in avehicle, information on software downloaded to the vehicle, includinglicense keys and software available for reinstallation of downloadedsoftware, and diagnostic information for the connected services. The oneor more information records may be organized according to a vehicle'sVIN. Accordingly, the VIN, once obtained from the vehicle, may betransmitted by the tool 100 over network 202 to the database 206 (viaserver 204) for retrieving vehicle information and transmitted back overnetwork 202 for output from tool 100. Further details of obtaining thediagnostic information will be described below.

Referring back to FIG. 2A, vehicle identification information may alsobe obtained wirelessly through wireless tool connection 106. Referringto FIG. 2B, which illustrates a dissected view of the tool 100illustrated in FIG. 2A, tool 100 may include one or more modules forgenerating a wireless connection. Two non-limiting examples include aWiFi module 106 a and/or a BLUETOOTH module 106 b. The WiFi module 106 amay transmit signals for connecting to wireless router 73. The BLUETOOTHmodule/transceiver 106 b may transmit signals for pairing with vehicletransceiver 15. An example of a BLUETOOOTH module 30 is one manufacturedby FREE2MOVE, part number F2M03MLA. It will be appreciated that tool 100may include one or more additional wireless modules arranged in anycombination and these examples are non-limiting and illustrative.

Vehicle identification information (e.g., and without limitation, a VIN)may be obtained via the wireless connection in a similar mannerdescribed above with respect to when the tool 100 is connected to theVCS 1 using wired connection 112. A wireless connection 106 may begenerated automatically or manually. For example, the connection 106 maybe generated once the tool 100 is in the vicinity of the vehicle. Uponmaking the connection, the vehicle information may be transmitted.Alternatively or additionally, a wireless connection may be generatedmanually via a selection of one or more of buttons 114. It should beunderstood that the arrangement of components illustrated in FIGS. 2Aand 2B is non-limiting and can be modified and re-arranged withoutdeparting from the spirit of the invention.

A user (e.g., and without limitation, a service technician) may manuallyactivate a wireless connection by one or more of buttons 114 (FIG. 2A)when the user is in a range that tool 100 can communicate with VCS 1. Inone embodiment, a wireless connection is generated once the tool 100 isin the vicinity of the VCS 1. The user may select one of the button(s)114 and, upon selection, a signal may be transmitted to microprocessor116 (FIG. 2B) which is in electrical communication 118 with the one ormore wireless modules 106 a, 106 b. Microprocessor 116 may transmit oneor more instructions via an electrical signal to the one or morewireless modules 106 a, 106 b for generating a wireless connection. Inone embodiment, a return signal may be transmitted to the tool 100confirming that a connection has been established. Upon establishing aconnection, the identification information may be transmitted to thevehicle information database 206 for obtaining vehicleinformation/diagnostic information as described above.

It should be understood that button(s) 114 may be push button(s),graphical buttons (e.g., buttons on a touch screen display), or otherbutton(s). Button(s) 114 may also be used for diagnosing otherconnections. For example, and without limitation, a user may insertadapter 108 for testing the in-vehicle memory card reader. As anothernon-limiting example, a diagnostic device may be inserted into adapterslot 110 of the tool 100. Upon insertion, the user may then press one ormore of button(s) 114 to begin testing. Signal(s) may be transmitted toand from microprocessor 116 and to and from adapter 108 and/or slot 110for performing a diagnosis.

Tool 100 may also include diagnostic software for diagnosing one or moreconnected services. In one embodiment, tool 100 may include software foreach connected service module. Thus, the WiFi module 106 a may includesoftware 120 a for confirming that a wireless connection can beestablished between the tool 100 and the vehicle. Similarly, theBLUETOOTH module may also include software 120 b for confirming that awireless connection can be established. Additionally, adapter slot 110may communicate with software 120 c for confirming the proper operationof media that is inserted into slot 110 or inserted into a receivingadapter. Additionally or alternatively, the software may be incommunication with microprocessor 116 which may send instructions to thesoftware for testing and diagnosing one or more connected servicescomponents. In one embodiment, the software maybe written to themicroprocessor 116 for performing testing and diagnosis. Accordingly, itshould be understood that the structure and arrangement for confirmingoperation of the one or more connected services modules is non-limitingand other structure(s) and arrangement(s) may be utilized as is known inthe art.

In one embodiment, tool 100 may also include a data cable 122 (e.g., andwithout limitation, a USB cable). Data cable 122 may be utilized inorder to receive information from a remote source (e.g., the vehicleinformation database 206) and transfer information to the vehicle. Forexample, tool 100 may be connected to a personal computer (PC) or otherremote terminal (e.g., a nomadic device) for receiving software todownload the VCS 1. The tool 100 may receive software from the vehicleinformation database 206 using the vehicle identification information(e.g., the VIN) received from the vehicle (either via a wired orwireless connection as described above).

In one embodiment, the tool 100 may alternatively or additionallyreceive applications purchased by a vehicle-owner, and the respectivelicense keys, from a purchased applications site (e.g., a website). Inthis latter embodiment, the vehicle-owner may have pre-purchasedapplications for use in the vehicle from the purchased applicationswebsite. The purchased applications may be stored at the purchasedapplication site after purchase until the application(s) are downloadedto tool 100. In another embodiment, the purchased applications may bedownloaded to the VCS 1 over a network connection (e.g., the Internet)upon purchase, but may not be operable until the license keys have beenreceived. The tool 100 may be used to obtain the license keys from thepurchased application website.

The tool 100 may then transfer the downloaded data to the vehicle. Thetransfer may be accomplished using a wired connection (e.g., via datacable 122) or wirelessly.

Tool 100 may optionally include one or more LED lights 124 forindicating which connected service is being tested/diagnosed (e.g.,based on the button that is pressed). One or more diagnostic messagesmay also be output using the LEDs 124 (in addition to or as analternative to displaying from display 102 or outputting from speaker104). For example, if a button 114 is pressed to test a WiFi connection,the resulting status may be output via one or more LED lights 124. Themessage may be output as one or more light flashes from a correspondingLED, color changes representing the status, or a pattern of flashing andcolor changes from one or more of the lights 124. It should beunderstood that these examples are non-limiting and other methods ofoutputting a message may be utilized.

The status messages (whether output from the display 102, speaker 104and/or LEDs 124) may be presented as pass or fail. A pass/fail messagemay be a numeric message (e.g., 1=pass, 0=fail), alphabetic (e.g.,A=pass, B=fail), alphanumeric, associated with certain colors, output ina spoken language, and/or displayed as text.

In one embodiment, tool 100 may be a web-based tool. The user mayperform the various diagnostics as described above from any remoteterminal including, but not limited to, a personal computer or nomadicdevice (e.g., a mobile phone, PDA, etc). Accordingly, the transfer ofdata to and from the vehicle (as described above), and the diagnostics,may be a seamless, transparent process to the user.

FIG. 4 illustrates a process for testing the one or more connectedservices in a vehicle. It will be appreciated that the disclosure andarrangement of FIG. 4 may be modified or re-arranged to best fit aparticular implementation of the various embodiments of the invention.

As illustrated in block 300, a wired or wireless connection is made withthe vehicle. Proceeding to block 302, one or inputs are received to testone or more connected services. The one or more inputs may be receivedfrom the button(s) 114.

One or more services for testing may be determined based on and/or inresponse to the received input(s) as illustrated in block 304. The oneor more connected services may be tested/diagnosed sequentially (in anyorder) or in parallel. Accordingly, while FIG. 4 illustrates thediagnostic flow as occurring sequentially, this illustration serves asan example and should not be considered non-limiting.

In one embodiment, a diagnostic connection (wired or wireless) to thevehicle information database 206 may also be established, as illustratedin block 306, at or around the same time as the service(s) to be testedare determined (block 304). As described above, the wired connection tothe vehicle information database 206 may be generated and establishedvia a connection between data cable 122 and a remote terminal (e.g., PCor nomadic device).

As illustrated in block 308, vehicle identification information may beextracted from the vehicle and received for transmission to the vehicleinformation database 206. In one embodiment, the vehicle identificationinformation may be received before the connection is established withthe vehicle information database 206.

The vehicle identification information may be transmitted to the vehicleinformation database 206 as illustrated in block 310. The VIN may beused to look up and extract the vehicle data from the vehicleinformation database 206. The vehicle data may be received from thevehicle information database 206 as illustrated in block 312.

As stated above, vehicle data may include any information about thevehicle. By way of example and not limitation, vehicle diagnostic datamay include vehicle diagnostic information, information on connectedservices available in the vehicle, information on software in thevehicle, test data for testing the one or more connected services, andother information related to the vehicle.

In one embodiment, all vehicle diagnostic data for the vehicle isreceived by the tool 100 from vehicle information database 206. The datais then parsed by the tool 100 to determine a diagnostic status. Inanother embodiment, the vehicle data is parsed by the server 204 and thediagnostic status is downloaded by the tool 100 for output to the user.As an example, the data may be parsed to find vehicle diagnostic datathat passes and/or fails based on the diagnostic information receivedfrom the connected services of the vehicle. The diagnostic informationmay include, for example (without limitation), diagnostic trouble codes(or other diagnostic testing identifiers) associated with the connectedservices. With respect to software, it should be understood thatsoftware that is not in the vehicle may generate a fail status andsoftware that is in the vehicle may generate a pass status. Othermethods of extracting the relevant data may be utilized withoutdeparting from the scope and spirit of the invention.

In one embodiment, where a fail status is generated, the diagnosticinformation in database 206 may also include information on a cause forthe fail status. Potential causes for a fail status may include a breakin wireless communication (i.e., no data transmission), corruptsoftware, unreadable media, and/or a malfunction in the memory cardreader. It should be understood that these examples are non-limiting. Inone embodiment, the diagnostic information in database 206 may be storedas a series of number and/or letters (or in another non-limiting codeform) which may be translated by the server 204 and/or tool 100 forcomprehension by the user.

Determining which service to test/diagnose may include determining ifBLUETOOTH is to be tested as illustrated in block 314. The test may beinitiated automatically (e.g., in a sequence programmed to the tool 100)and/or manually (e.g., a button 114 representing a WiFi test isselected). A test signal may be transmitted to the BLUETOOTH module 106b for transmission to the BLUETOOTH transceiver 15 in the vehicle inorder to test the BLUETOOTH communication channel as illustrated inblock 318. Prior to, or as a part of, transmitting the test signal, thetool 100 may be paired with the BLUETOOTH transceiver 15 in the vehicle31, as indicated at block 316. Pairing mode is entered at tool 100 bydepressing one or more button(s) 114 which may be a BLUETOOTH pairbutton. The vehicle 31 may also include a BLUETOOTH pairing button 52which may be also pressed to complete the pairing operation.

During testing, a test message for the BLUETOOTH connection may betransmitted to BLUETOOTH module 106 b for wireless communication to theBLUETOOTH transceiver 15 within vehicle 31. The message may be playedback at speaker 104 as indicated at block 340. In one embodiment, theresult may be in one or more languages including, but not limited to,English, French and Spanish. A message may state, for example, “This isa test of the BLUETOOTH communication channel. Data transmission issuccessful.” Prior to outputting the message, a determination may bemade whether the test signal was transmitted successfully as illustratedin block 338. Accordingly, if this message is heard by a user, theBLUETOOTH communication channel is determined to be operational asdetermined by the message output from the speaker 104. If the message isnot heard, the BLUETOOTH service is not operating.

In one embodiment, diagnostic information may be retrieved from thevehicle information database 206 for the BLUETOOTH channel asillustrated in block 334. The diagnostic information may be received bythe tool 100 and the diagnostic status may be determined based on thediagnostic information as illustrated in block 336. A non-limitingexample of a diagnostic status may be that a paired connection cannot begenerated between the tool 100 and the vehicle 31. The status may or maynot also include a reason that the tool 100 is unable to establish apaired connection (e.g., and without limitation, software and/orhardware problem). The diagnostic status may be output from the tool 100and/or output from speaker 104 as illustrated in block 340.

As illustrated in block 320, the WiFi communication channel may also betested. The test may be initiated automatically (e.g., in a sequenceprogrammed to the tool 100) and/or manually (e.g., a button 114representing a WiFi test is selected). A WiFi connection may begenerated as illustrated in block 322. A test signal may be transmittedto the WiFi module 106 a for transmission to the router 73 in thevehicle in order to test the WiFi communication channel as illustratedin block 324. The WiFi connection may be generated prior to, or as apart of, transmitting the test signal. A WiFi connection is entered attool 100 by depressing one or more button(s) 114 which may be a WiFibutton.

During testing, a test message for the WiFi connection may betransmitted to WiFi module 106 a for wireless communication to therouter 71 within vehicle 31. The message may be played back at speaker104 as indicated at block 340. In one embodiment, the result may be inone or more languages including, but not limited to, English, French andSpanish. A message may state, for example, “This is a test of the WiFicommunication channel. Data transmission is successful.” Prior tooutputting the message, a determination may be made whether the testsignal transmitted successfully as illustrated in block 338. If thismessage is heard by a user, the WiFi communication channel is determinedto be operational as determined by the message output from the speaker104. If the message is not heard, the WiFi service is not operating.

In one embodiment, diagnostic information may be retrieved from thevehicle information database 206 for the WiFi communication channel asillustrated in block 334. The diagnostic information may be received bythe tool 100 and the diagnostic status may be determined based on thediagnostic information as illustrated in block 336. A non-limitingexample of a diagnostic status may be that a WiFi connection cannot begenerated between the tool 100 and the vehicle 31. The status may or maynot also include a reason that the tool 100 is unable to connect (e.g.,and without limitation, software and/or hardware problem). Thediagnostic status may be output from the tool 100 and/or output fromspeaker 104 as illustrated in block 340.

Storage media and/or an in-vehicle memory card reader may also be testedas illustrated in block 326. Tool 100 may test storage media (e.g., amemory card as illustrated in FIG. 4) inserted into slot 110 and/or testa memory card reader in vehicle 31. The test may be initiatedautomatically (e.g., in a sequence programmed to the tool 100) and/ormanually (e.g., a button 114 representing a WiFi test is selected). Adetermination may be made whether the adapter port 110 has received astorage media adapter and/or the memory card reader adapter 108 has beeninserted as illustrated in block 328. If not, the user may be requiredto do so as illustrated in block 330. In one embodiment, a message maybe transmitted to the user instructing the user to insert an adapter toadapter port 110 and/or adapter 108. The message may be, withoutlimitation, textual (e.g., displayed at display 102), verbal, a tone, abeep, or combinations thereof. Alternatively or additionally, the tool100 may suspend testing until the adapter is received at adapter port110 and/or adapter 108 is inserted. In one embodiment, as describedbelow, the insertion status may be determined during testing.

A test signal may be transmitted to the memory adapter slot 110 and/orthe in-vehicle memory card reader as illustrated in block 332. A test ofthe memory card and/or the memory card reader may be performed bypressing button(s) 114 which may activate such testing.

During testing, a test message may be played back at speaker 104, asindicated at block 340, identifying the test result. In one embodiment,the result may be in one or more languages including, but not limitedto, English, French and Spanish. A message may state, for example, “Thisis a test of the memory card. Data transmission is successful.” Asimilar message may be output for testing the in-vehicle memory cardreader. Prior to outputting the message, a determination may be madewhether the test signal transmitted successfully as illustrated in block338. If this message is heard by a user, the storage media/in-vehiclecard reader is determined to be operational as determined by the messageoutput from the speaker 104. If the message is not heard, the storagemedia/in-vehicle card reader is not operating.

In one embodiment, diagnostic information may be retrieved from thevehicle information database 206 for the storage media/in-vehicle cardreader as illustrated in block 334. The diagnostic information may bereceived by the tool 100 and the diagnostic status may be determinedbased on the diagnostic information as illustrated in block 336. Anon-limiting example of a diagnostic status may be that data cannot beread on the memory card. The status may or may not also include a reasonthat the tool 100 is unable to read the memory card (e.g., and withoutlimitation, software and/or hardware problem). As another non-limitingexample, the status may relate to the memory card reader in the vehicle31. As another non-limiting example, the status may be that a memorycard and/or card reader adapter is not connected. The diagnostic statusmay be output from the tool 100 and/or output from speaker 104 asillustrated in block 340.

It should be understood that the arrangement of FIG. 4 is illustrativeand should not be considered limiting. For example, the connectedservices may be tested in any order and/or may be tested sequentially orin parallel. Additionally, other connected services components may betested including, but not limited to, testing audio sound quality and/orspeakers, GPS, and/or software applications installed to the VCS 1 invehicle 31. In testing software applications, tool 100 may test for thepresence of applications purchased and/or installed by the vehicle ownerand/or the presence of license keys for the installed applications. Bycommunicating with the vehicle information database 206 (as illustratedin FIG. 4), tool 100 may determine the status of the purchased softwareand, if necessary, correct any software issues. For example, and withoutlimitation, if any purchased application is missing a license key, tool100 may retrieve the appropriate license key for installation to VCS 1.As another non-limiting example, if a purchased application is missingor not functioning, tool 100 may retrieve the software forre-installation to VCS 1.

While embodiments of the invention have been illustrated and described,it is not intended that these embodiments illustrate and describe allpossible forms of the invention. Rather, the words used in thespecification are words of description rather than limitation, and it isunderstood that various changes may be made without departing from thespirit and scope of the invention.

While exemplary embodiments are described above, it is not intended thatthese embodiments describe all possible forms of the invention. Rather,the words used in the specification are words of description rather thanlimitation, and it is understood that various changes may be madewithout departing from the spirit and scope of the invention.Additionally, the features of various implementing embodiments may becombined to form further embodiments of the invention.

What is claimed is:
 1. A method comprising: establishing a connectionbetween a testing tool and a vehicle computing system (VCS), over aconnection to be tested; reporting connection errors identified duringthe establishing; transmitting a message, over the establishedconnection, including instructions for message playback over a vehicleaudio system, the message identifying the connection; determining if themessage transmission was successful; reporting message transmissionerrors; and reporting diagnostic information relating to theestablishing and transmitting.
 2. The method of claim 1, wherein theconnection includes a BLUETOOTH connection.
 3. The method of claim 2,wherein the message includes spoken identification of the BLUETOOTHconnection.
 4. The method of claim 1, wherein the connection includes aWiFi connection.
 5. The method of claim 4, wherein the message includesspoken identification of the WiFi connection.
 6. The method of claim 1,wherein the connection includes a storage media reader.
 7. The method ofclaim 6, wherein the message includes spoken identification of thestorage media reader type.
 8. The method of claim 1, wherein the messageidentifies the connection through playback of a sound defined asidentifying the connection.
 9. A computer-readable storage medium,storing instructions that, when executed, cause an executing processorto perform a method comprising: establishing a connection between atesting tool and a vehicle computing system (VCS), over a connection tobe tested; reporting connection errors identified during theestablishing; transmitting a message, over the established connection,including instructions for message playback over a vehicle audio system,the message identifying the connection; determining if the messagetransmission was successful; reporting message transmission errors; andreporting diagnostic information relating to the establishing andtransmitting.
 10. The storage medium of claim 9, wherein the connectionincludes a BLUETOOTH connection.
 11. The storage medium of claim 10,wherein the message includes spoken identification of the BLUETOOTHconnection.
 12. The storage medium of claim 9, wherein the connectionincludes a WiFi connection.
 13. The storage medium of claim 12, whereinthe message includes spoken identification of the WiFi connection. 14.The storage medium of claim 9, wherein the connection includes a storagemedia reader.
 15. The storage medium of claim 14, wherein the messageincludes spoken identification of the storage media reader type.
 16. Thestorage medium of claim 9, wherein the message identifies the connectionthrough playback of a sound defined as identifying the connection.
 17. Asystem comprising: a processor configured to: establish a connectionbetween a testing tool and a vehicle computing system (VCS), over aconnection to be tested; report connection errors identified during theestablishing; transmit a message, over the established connection,including instructions for message playback over a vehicle audio system,the message identifying the connection; determining if the messagetransmission was successful; report message transmission errors; andreport diagnostic information relating to the establishing andtransmitting.
 18. The system of claim 17, wherein the connectionincludes a BLUETOOTH connection.
 19. The system of claim 17, wherein theconnection includes a WiFi connection.
 20. The system of claim 17,wherein the connection includes a storage media reader.